Skip to content

A11y Bug 10987406: Announce actual font size value on increase/decrease in Article mode.#669

Merged
aanchalbhansali merged 3 commits into
masterfrom
copilot/fix-screen-reader-font-size-announcement
Jul 7, 2026
Merged

A11y Bug 10987406: Announce actual font size value on increase/decrease in Article mode.#669
aanchalbhansali merged 3 commits into
masterfrom
copilot/fix-screen-reader-font-size-announcement

Conversation

Copilot AI commented Jul 6, 2026 •
edited by azure-boards Bot
Loading

Copy link
Copy Markdown
Contributor

Screen readers announced only static labels ("Increase font size" / "Decrease font size") when users adjusted font size in Article mode — never the updated value, leaving assistive technology users without feedback on the current state.

Changes

  • New localized template strings in the strings object:

    • fontSizeDecreasedTo → "Font size decreased to {0}"
    • fontSizeIncreasedTo → "Font size increased to {0}"

  • Updated font size click handlers to substitute the actual articleFontSize value at announcement time:

// Before
announceToScreenReader(strings.decreaseFontSize); // "Decrease font size"

// After
announceToScreenReader(strings.fontSizeDecreasedTo.replace("{0}", "" + articleFontSize));
// → "Font size decreased to 14"

Follows the existing {0}-replacement pattern used by pdfPageProgress and similar dynamic announcements in the renderer.

Original prompt

[OneNote Clipper] [Web] [Screen reader]: Screen reader is not announcing increase and decrease font size value.

Work Item Details

Note: Please focus on the descriptions and information that provide context about the task requirements, functionality, and implementation details. Dates, priorities, and administrative metadata are less relevant for coding tasks.

Description

Environment Details:

Application Name: OneNote Clipper-web

Platform: Web

OS Version: 25H2(26200.7392)

Edge Version: 143.0.3650.96 (Official build) (64-bit)

Application URL: https://www.onenote.com/clipper

Repro Steps:

  1. Open https://www.onenote.com/clipper.

  2. Navigate till get one note web clipper for edge and activate it.

  3. Edge Add-ons page will appear. Invoke the Get button.

  4. OneNote Clipper will be added in edge extension section. 

  5. Expand the Extension button and turn on the OneNote Clipper Show in Toolbar button.

  6. Now invoke the OneNote clipper button.

  7. Open in sign in page, 

  8. Navigate to "Article" button, invoke it.

  9. Navigate to "increase and decrease font size value.

  10. Observe the issue.

Actual Result:

When the user selects Increase Font Size or Decrease Font Size, the screen reader does not announce the updated font size value.

Expected Result:

After the user increases or decreases the font size, the screen reader should announce the updated font size value (e.g., “Font size increased to 14” or “Font size decreased to 12”).

User Impact:

Users with low vision, color vision deficiencies, or those relying on High Contrast mode cannot determine the current focus or selected item.

Have feedback on bugs logged, please tag bug as “A11yRCA” and add your feedback in the comment section.

Tags

A11yRT; A11yUsable; Accessibility; OneNoteClipper_Web; RT-122025; RT-OneNote Clipper-Web-Dec2025; TCS-E+D

RCA Analysis

Was change validated in devMain first before porting to fork?

Why was Flighting|Backout not used?

Impact of bug (# users affected):

RCA and Mitigation/Fix Details:

What are you doing to prevent this in the future?

Work item: AB#10987406
Created via Azure DevOps

fix: announce updated font size value to screen reader on increase/de…
fb28f76 
…crease

When users click the increase or decrease font size buttons in Article
mode, the screen reader now announces the updated font size value (e.g.
"Font size increased to 18" or "Font size decreased to 14") instead of
the generic static labels.

Two new localized template strings are added:
  WebClipper.Accessibility.ScreenReader.FontSizeIncreasedTo
  WebClipper.Accessibility.ScreenReader.FontSizeDecreasedTo

The {0} placeholder is replaced with the current articleFontSize value
at announcement time, matching the pattern used by other dynamic
announcements in the codebase (e.g. pdfPageProgress).
Copilot AI changed the title [WIP] Fix screen reader announcement for font size changes fix(a11y): announce actual font size value on increase/decrease Jul 6, 2026
Copilot AI requested a review from aanchalbhansali July 6, 2026 17:57
@aanchalbhansali aanchalbhansali marked this pull request as ready for review July 6, 2026 18:34
@aanchalbhansali aanchalbhansali changed the title fix(a11y): announce actual font size value on increase/decrease A11y Bug 10987406: Announce actual font size value on increase/decrease Jul 7, 2026
@aanchalbhansali aanchalbhansali changed the title A11y Bug 10987406: Announce actual font size value on increase/decrease A11y Bug 10987406: Announce actual font size value on increase/decrease in Article mode. Jul 7, 2026
@aanchalbhansali

aanchalbhansali commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

@copilot resolve the merge conflicts in this pull request....please keep both the master branch changes and this branch changes

Merge remote-tracking branch 'origin/master' into copilot/fix-screen-…
114131a 
…reader-font-size-announcement

# Conflicts:
#	src/scripts/renderer.ts

Copilot AI commented Jul 7, 2026

Copy link
Copy Markdown
Contributor Author

@copilot resolve the merge conflicts in this pull request....please keep both the master branch changes and this branch changes

Merge conflicts resolved in 114131a. The font size click handlers now include both updateFontSizeButtonStates() from master and the improved announceToScreenReader calls with the actual font size value from this branch.

Copilot AI requested a review from aanchalbhansali July 7, 2026 05:55
@aanchalbhansali aanchalbhansali merged commit 94c896e into master Jul 7, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@KethanaReddy7 KethanaReddy7 KethanaReddy7 approved these changes
+1 more reviewer
@aanchalbhansali aanchalbhansali aanchalbhansali approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

@aanchalbhansali aanchalbhansali

Copilot code review Copilot

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@aanchalbhansali @KethanaReddy7